| 1. | Research on observer pattern applied in telecommunications management network system
面向业务的综合网管系统的研究与实现 |
| 2. | I ll start by looking at how to implement this requirement without using the object - oriented observer pattern
首先介绍不使用面向对象的observer模式时如何实现该要求。 |
| 3. | " for more about using aspects and a refactored library observer pattern to track the use of a service
” ，获得有关使用方面和已重构的library observer模式来跟踪服务使用状况的详细信息。 |
| 4. | Use the observer pattern to decouple the generation of gui events from their semantics within a given application
）使用观察者模式消除了gui事件生成与它们在指定应用程序中的语义之间的耦合。 |
| 5. | The swing framework makes extensive use of the observer pattern also known as the publish - subscribe pattern in the form of event listeners
） swing框架以事件侦听器的形式广泛利用了观察者模式（也称为发布-订阅模式） 。 |
| 6. | The observer pattern , most often seen in swing development , is also very useful for decoupling components in situations other than gui applications
观察者模式在swing开发中很常见，在gui应用程序以外的场景中，它对于消除组件的耦合性也非常有用。 |
| 7. | Whenever you use the observer pattern , you are coupling two separate components - the observer and the observed , which generally have distinct lifecycles
不管什么时候使用观察者模式，都耦合着两个独立组件观察者和被观察者，它们通常有不同的生命周期。 |
| 8. | Describes the observer pattern as defining " a one - to - many dependency between objects so that when one object changes state , all of its dependents are notified and updated automatically . " the observer pattern enables loose coupling of components ; components can keep their states synchronized without necessarily needing direct knowledge of each other s identities or internals , facilitating component reuse
）把观察者模式描述为：定义对象之间的“一对多”关系，这样一个对象改变状态时，所有它的依赖项都会被通知，并自动更新。观察者模式支持组件之间的松散耦合；组件可以保持它们的状态同步，却不需要直接知道彼此的标识或内部情况，从而促进了组件的重用。 |
